Layer-3 performance monitoring sectionalization

ABSTRACT

A method is disclosed for the collection of performance metrics by establishing service operations administration and maintenance (OAM) sessions between an actuator and a plurality of reflectors in a communication network. Test packets from an actuator simultaneously reach a plurality of reflectors along a test path. Each single test packet results into a plurality of test results, one per reflector, with quasi-synchronous performance metrics to sectionalize a network and more efficiently isolate fault or performance problems without the need for additional test packets to isolate the issue. Another method is disclosed wherein an actuator generates and transmits a plurality of simultaneous test packets, one per NID device, resulting into a plurality of test results, one per reflector, with quasi-synchronous performance metrics to sectionalize a network and more efficiently isolate fault or performance problems without the need for additional test packets to isolate the issue.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 13/840,404, filed Mar. 15, 2013, now allowed, which claims priority to U.S. Provisional Application No. 61/758,370, filed Jan. 30, 2013, each of which is hereby incorporated by reference herein in its entirety.

TECHNICAL FIELD

The present disclosure relates generally to computer processing environments and, in some embodiments, more particularly to processor-executable instructions, such as program modules, being executed in a distributed computing environment.

BRIEF SUMMARY

Aspects of this disclosure relate to sectionalization of a communication network for the purpose of improving the isolation of faults and the collection of performance monitoring metrics with modified Two-Way Active Measurement Protocol (TWAMP) requests and replies and without requiring explicit layer-3 addressing information of the devices implementing the reflector function in the context of an Operations Administration and Maintenance (OAM) framework. Additional information can be found, for example, in U.S. patent application Ser. No. 13/557,138, which was filed on Jul. 24, 2012, and U.S. patent application Ser. No. 13/552,063, which was filed on Jul. 18, 2012, each of which is incorporated herein by reference in its respective entirety and for all purposes.

One aspect of the present disclosure is directed to a method of establishing service operations administration and maintenance (OAM) sessions between an actuator and a plurality of reflectors for the purpose of collecting performance metrics. The collected performance metrics can then be used to sectionalize a network for the purpose of improving the isolation of faults and performance problems.

A further aspect of this disclosure is directed to a method of reaching a plurality of reflectors with a single test packet where a test packet is forwarded by a reflector to a next reflector in the downstream direction along a test path and where each reflector replies directly to the actuator with the requested performance metrics. In order to simplify the installation and the operation of the reflectors, these reflectors do not require unique layer-3 addressing information. Instead, they borrow the IP address of another device downstream to the last reflector along the test path.

According to an additional aspect of the present disclosure, a system is disclosed for assigning a test reply from a reflector to the appropriate reflector where a sequence number is redefined to include a unique reflector identifier. The reflector identifier is either assigned statically for each reflector or it can be dynamically determined.

Aspects of the present disclosure are also directed to a method of establishing service operations administration and maintenance (OAM) sessions between an actuator and a plurality of reflectors in a communication network. The method includes: continuously monitoring, by one or more of the reflectors, any test packets transmitted by the actuator; transmitting by the actuator a test packet to a first one of the reflectors; forwarding, by the first reflector, the test packet to a second one of the reflectors next along a test path with respect to the first reflector; generating, by each of the first and second reflectors, a test reply to the actuator, each of the test replies generated back to the actuator incorporating a unique reflector identifier; and, using the test replies to the test packet to sectionalize the communication network to isolate faults and performance problems.

In some embodiments, each unique reflector identifier is defined automatically by the reflector, for example, via a signaling exchange which may include a TWAMP control plane or via a configuration method, such as CLI, web-based configuration, and/or XML.

In some embodiments, each unique reflector identifier can be created by repurposing an uplink sequence number and using some of the bits of an uplink sequence number to encode a unique reflector identifier.

Other aspects of the present disclosure are directed to a system for establishing service operations administration and maintenance (OAM) sessions between an actuator and a plurality of reflectors in a communication network.

Additional aspects are directed to non-transient computer-readable storage media with processor-executable instructions for carrying out any of the methods disclosed herein.

The above summary is not intended to represent each embodiment or every aspect of the present disclosure. Rather, the summary merely provides an exemplification of some of the novel features presented herein. The above features and advantages, and other features and advantages of the present disclosure, will be readily apparent from the following detailed description of exemplary embodiments and modes for carrying out the present invention when taken in connection with the accompanying drawings and the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other advantages of the present disclosure will become apparent upon reading the following detailed description and upon reference to the drawings.

FIG. 1 illustrates a representative mobile network of a mobile operator;

FIG. 2 illustrates the insertion of a plurality of representative Network Interface Devices (NID) and a representative Two-Way Active Measurement Protocol (TWAMP) Actuator into the mobile network of a mobile operator;

FIG. 3 illustrates how a representative TWAMP Actuator and a plurality of representative NID's sectionalize a network to isolate faults and performance problems;

FIG. 4A illustrates the format of a representative TWAMP message data.

FIG. 4B is a representative diagram showing how a single TWAMP request can reach a plurality of NID's with a shared UDP port and without the need for an explicit layer-3 address;

FIG. 5 is a representative diagram showing how multiple synchronous TWAMP requests are generated to reach a plurality of NID (each with unique UDP port numbers) without the need for an explicit layer-3 address; and

FIG. 6 illustrates how an additional TWAMP Actuator can further help to sectionalize a network and isolate faults and performance problems.

While the invention is susceptible to various modifications and alternative forms, specific embodiments have been shown by way of example in the drawings and will be described in detail herein. It should be understood, however, that the invention is not intended to be limited to the particular forms disclosed. Rather, the invention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the invention as defined by the appended claims.

DETAILED DESCRIPTION

The following discussion is intended to provide a brief, general description of suitable computer processing environments in which the methods and apparatus described herein may be implemented. In one non-limiting example, the method and apparatus will be described in the general context of processor-executable instructions, such as program modules, being executed in a distributed computing environment in which tasks may be performed by remote and local processing devices linked via one or more networks. Those of ordinary skill in the art will appreciate that the method may be practiced with any number of suitable computer system configurations and is not limited to the described configurations.

The following discussion is intended to provide a brief, general description of suitable computer processing environments in which the methods and apparatuses described herein may be implemented. In one non-limiting example, one or more methods and apparatuses will be described in the general context of processor-executable instructions, such as program modules, being executed in a distributed computing environment in which tasks may be performed by remote and local processing devices linked via one or more networks. Those of ordinary skill in the art will appreciate that the methods may be practiced with any number of suitable computer system configurations and is not limited to the described configurations.

The Service OAM framework is defined in standards such as Two-Way Active Measurement Protocol (TWAMP), [RFC5357], ITU-T Y.1731 and IEEE 802.1ag. It allows efficient delay and packet loss measurements via a bi-directional measurement function, i.e., 2×OneWay with the capability to measure and report all required metrics (delay, jitter, loss, reorder, etc.) for both directions (forward path and reverse path) to determine and report on the performance of the network.

In some embodiments, there is a need for the various protocols used as part of an OAM framework to operate either directly over a Layer 2 network as well as when the Ethernet Services are offered over a Layer 3 network infrastructure (IPv4 and/or IPv6).

The appended diagrams and illustrations are used to illustrate how the TWAMP metrics can be retrieved from a plurality of Network Interface Devices (NID) without the need for explicit layer-3 addressing to reach the NID devices. The TWAMP Actuator is usually configured with an explicit layer-3 address.

FIG. 1 illustrates a simplified network 100 operated, for example, by a mobile operator where a remote EnodeB 101 is accessed via a network 110 (Multiprotocol Label Switching (MPLS), Ethernet, or other) that is either managed by the mobile operator or the by a 3^(rd) party operating organization. In the illustrated embodiment, the remote EnodeB 101 interfaces with an MSC Switch Site 102 that further interfaces with a Signaling Gateway (S-GW) 103 and a Packet Data Network Gateway (P-GW) 104. The ingress and egress into the 3^(rd) party layer-2 network 110 is handled by a pair of layer-2 switches 120 and 121.

FIG. 2 illustrates that a plurality of NID devices 201, 202, and 203 are added to the network 100 for the purpose of providing a reflector function to process TWAMP requests generated by a TWAMP Actuator 210. The NID devices 201, 202, 203 do not need a unique layer-3 address; instead, they can borrow the IP address of the EnodeB 101 or of any other device at the end of the test path in the downstream direction from the TWAMP Actuator 210.

FIG. 3 illustrates how the TWAMP Actuator 210 and the NID devices 201, 202, 203 can be used to sectionalize the network 100 to isolate faults and performance problems detected via TWAMP requests and replies between the TWAMP Actuator 210 and the NID devices 201, 202, 203. A TWAMP session 301 provides performance measurements end to end, but if there is a performance problem, the isolation of the problem may require additional tests to isolate the specific equipment or connection causing the problem. If the problem is transient, the subsequent tests may not be able to replicate the problem. Adding other simultaneous TWAMP sessions 302 and 303 and using the same TWAMP request over each of these sessions allow for a plurality of quasi-synchronous performance measurements, further increasing the likelihood of detecting and isolating the root cause of a transient performance problem. One-way and two-way packet delays and packet loss metrics can be measured for each TWAMP reply (one per TWAMP session 301, 302, 303) to determine which segment between a pair of NID devices 201, 202, 203 is responsible for the packet loss or for unacceptable delays. While the above may be achieved via a multiple of parallel TWAMP sessions, the correlation of the metrics is not as precise since each TWAMP session uses TWAMP requests that cannot reliably be correlated since their synchronicity cannot be assured.

FIG. 4A illustrates a format of the TWAMP data exchanged between the TWAMP Actuator 210 and the NID devices 201, 202, 203. Of particular interest, aspects of this disclosure redefine the encoding of an Uplink Sequence Number 400. This field is defined as a 32-bit unsigned sequence number for packets returned to the TWAMP Actuator 210 by an NID device 201, 202, 203. As discussed in this disclosure, NID devices 201, 202, 203 are not assigned a unique layer-3 address and may all share the same UDP port number. Bits 24 to 31 of the Uplink Sequence Number 400 are therefore re-assigned as a unique NID identifier 401 and the Uplink Sequence Number is encoded with bits 0 to 23. The value of the NID identifier 401 is either configured for each NID device 201, 202, 203 or dynamically determined by each NID device 201, 202, 203 during the automatic discovery process or at a later time.

FIG. 4B is an example of a protocol flow diagram that illustrates a flow of TWAMP messages between an Actuator 210 and NID devices 201, 202, 203. Looking at the flow diagram, the TWAMP Actuator 210 generates a first TWAMP Request 411 and encapsulates as a UDP packet. The UDP port number is set to a pre-agreed value and that reserved value is shared by each and every NID devices 201, 202, 203. The TWAMP Request 411 is addressed using the layer-3 address of a device that is located beyond the last NID device in the test path: in this example NID 201. The layer-3 address of the EnodeB device 101 located beyond NID 201 is determined, for example, as taught in U.S. patent application Ser. No. 13/552,063, which is incorporated herein by reference in its entirety and for all purposes. Upon receiving a first TWAMP request 411 at NID 203, NID 203 first determines whether it is the last NID device in the test path. In this example, it is not the last NID device and therefore forwards the TWAMP request 411 to the next NID device 202 in the test path. Before, during, or after forwarding the TWAMP request 411 to NID 202, NID 203 generates a TWAMP reply 412 with the requested performance metrics. TWAMP reply 412 includes a NID identifier 401 used by the TWAMP Actuator 210 to recognize that the TWAMP reply 412 originates from NID 203. The processing of TWAMP request 411 by NID 202 is similar to the processing by NID 203 where TWAMP request 411 is forwarded to NID 201 and where TWAMP reply 413 with the NID identifier 401 set to identify NID 202 and returned to the TWAMP Actuator 210. Upon receiving TWAMP request 411 at NID 201, NID 201 determines by configuration or otherwise that it is the last NID device in the test path and discards TWAMP request 411. NID 201 also generates TWAMP reply 414 with the NID identifier 401 back to the TWAMP Actuator 210.

By receiving multiple TWAMP replies 412, 413, and 414 from a single TWAMP request 411, it is possible to compare one-way and two-way delay information and packet loss information to efficiently determine the root cause of an unacceptable delay or of a packet loss without the need to generate additional TWAMP requests on different test paths, further increasing the probability of identifying and resolving transient problems that may otherwise be more difficult to isolate. Upon receiving TWAMP replies 412, 413, 414, the TWAMP Actuator 210 may determine that is should generate another TWAMP request/reply exchange with NID devices 201, 202, 203 in the test path by repeating the above steps as required. The TWAMP request 411 and the TWAMP replies 412, 413, 414 are transparently handled by any layer-2 switches 120, 121 in the test path as would any other packets destined to the EnodeB 101 or back to the TWAMP Originator 210.

An optional or alternative method to assign the NID identifier 401 is for the TWAMP Actuator 210 to set the NID identifier 401 to zero and for each NID 201, 202, 203 in the test path to increment the NID identifier 401 as it forwards the TWAMP request to the next NID in the downstream direction along the test path. A NID device will then copy this NID identifier 401 of the TWAMP request 411 into the TWAMP reply 412, 413, 414 to allow the TWAMP Actuator 210 to associate the TWAMP reply 412, 413, 414 to the appropriate NID (201, 202, 203).

FIG. 5 is another protocol flow diagram that illustrates an optional or alternative flow of TWAMP messages between an Actuator 210 and NID devices 201, 202, 203. Looking at the flow diagram, the TWAMP Actuator 210 generates a plurality of TWAMP Request 521, 522, and 523 with the smallest possible delay between them where they can be determined to almost be synchronous and encapsulates them as UDP packets. The UDP port number of each TWAMP request 521, 522, 523 can be set to a unique pre-agreed value for each NID device 201, 202, 203. The TWAMP Requests 521, 522, 523 are addressed using the layer-3 address of a device that is located beyond the last NID device in the test path: in this example, NID 201. The layer-3 address of the EnodeB device 101 located beyond NID 201 is determined, for example, as taught in U.S. patent application Ser. No. 13/552,063 and is the IP address shared by each NID 201, 202, 203. Upon receiving a first TWAMP request 521 at NID 203, NID 203 generates a TWAMP reply 531 with the requested performance metrics. The processing of TWAMP request 522 by NID 202 is similar to the processing by NID 203 where TWAMP reply 532 is prepared by NID 202 and returned to the TWAMP Actuator 210. Upon receiving TWAMP request 523 at NID 201, NID 201 generates TWAMP reply 533 back to the TWAMP Actuator 210.

By receiving multiple TWAMP replies 531, 532, and 533, it is possible to compare one-way and two-way delay information and packet loss information to efficiently determine the root cause of an unacceptable delay or of a packet loss, further increasing the probability of identifying and resolving transient problems that may otherwise be more difficult to isolate. Upon receiving TWAMP replies 531, 532, 533, the TWAMP Actuator 210 may determine that is should generate another TWAMP request/reply exchange with NID devices 201, 202, 203 in the test path by repeating the above steps as required. The TWAMP requests 522, 523 addressed for NID devices 201, 203 located on the opposite side of network 110 are transparently handled by layer-2 switches 120, 121 in the test path as would any other packets destined to the EnodeB 101 or back to the TWAMP Originator 210.

Looking at FIG. 6, it illustrates how the addition of another TWAMP Actuator 610 judiciously placed at the MSC Switch Site 102 can be used to further sectionalize the network 100 and complement the ability to isolate faults and performance issues when compared to using a single TWAMP Actuator 210. Adding TWAMP Actuator 610 results into additional TWAMP sessions 601, 602, and 603 toward NID devices 201, 202, 203 and TWAMP session 604 between TWAMP Actuators 210, 610, where the TWAMP Actuators 210, 610 are also capable of acting as a TWAMP Reflectors in the same way as NID devices 201, 202, 203. Looking again at FIG. 6, one can see that there are now enough TWAMP sessions 301, 302, 303, 601, 602, 603, 604 to cover each and every segments of network 100 under the control of the mobile operator.

One or more or all of the embodiments described herein can be applicable to software-based, HW-based and pluggable (FPGA) Actuators and NID devices.

The present disclosure includes systems having processors to provide various functionalities to process information and to determine results based on inputs. Generally, the processing may be achieved with a combination of hardware and software elements. The hardware aspects may include combinations of operatively coupled hardware components including, for example, microprocessors, logical circuitry, communication/networking ports, digital filters, memory, and/or logical circuitry. The processors may be adapted to perform operations specified by a computer-executable code, which may be stored on a computer-readable medium.

The steps of the methods described herein may be achieved via an appropriate programmable processing device, such as an external conventional computer or an on-board field programmable gate array (FPGA) or digital signal processor (DSP), which executes software, or stored instructions. In general, physical processors and/or machines employed by embodiments of the present disclosure for any processing or evaluation may include one or more networked or non-networked general purpose computer systems, microprocessors, field programmable gate arrays (FPGA's), digital signal processors (DSP's), micro-controllers, and the like, programmed according to the teachings of the exemplary embodiments of the present disclosure, as is appreciated by those skilled in the art. Appropriate software can be readily prepared by programmers of ordinary skill based on the teachings of the exemplary embodiments, as is appreciated by those skilled in the art. In addition, the devices and subsystems of the exemplary embodiments can be implemented by the preparation of application-specific integrated circuits or by interconnecting an appropriate network of conventional component circuits, as is appreciated by those skilled in the art. Thus, the exemplary embodiments are not limited to any specific combination of hardware circuitry and/or software.

Stored on any one or on a combination of computer readable media, the exemplary embodiments of the present disclosure may include software for controlling the devices and subsystems of the exemplary embodiments, for driving the devices and subsystems of the exemplary embodiments, for processing data and signals, for enabling the devices and subsystems of the exemplary embodiments to interact with a human user, and the like. Such software can include, but is not limited to, device drivers, firmware, operating systems, development tools, applications software, and the like. Such computer readable media further can include the computer program product of an embodiment of the present disclosure for performing all or a portion (if processing is distributed) of the processing performed in implementations. Computer code devices of the exemplary embodiments of the present disclosure can include any suitable interpretable or executable code mechanism, including but not limited to scripts, interpretable programs, dynamic link libraries (DLLs), Java classes and applets, complete executable programs, and the like. Moreover, parts of the processing of the exemplary embodiments of the present disclosure can be distributed for better performance, reliability, cost, and the like.

Common forms of computer-readable media may include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, any other suitable magnetic medium, a CD-ROM, CDRW, DVD, any other suitable optical medium, punch cards, paper tape, optical mark sheets, any other suitable physical medium with patterns of holes or other optically recognizable indicia, a RAM, a PROM, an EPROM, a FLASH-EPROM, any other suitable memory chip or cartridge, a carrier wave or any other suitable medium from which a computer can read.

While particular implementations and applications of the present disclosure have been illustrated and described, it is to be understood that the present disclosure is not limited to the precise construction and compositions disclosed herein and that various modifications, changes, and variations can be apparent from the foregoing descriptions without departing from the spirit and scope of the invention as defined in the appended claims. 

What is claimed is:
 1. A method of establishing service operations administration and maintenance (OAM) sessions in a communication network, the method comprising: monitoring, by a first reflector and a second reflector, any test packets transmitted by an actuator which contain a predetermined identifier, the predetermined identifier comprising a layer 2 actuator address, the first reflector being located downstream along a test path with respect to the actuator, the second reflector being located downstream along a test path with respect to the first reflector; transmitting by the actuator a first test packet and a second test packet, the first test packet configured with the predetermined identifier and a first unique reflector identifier, the second test packet configured with the predetermined identifier and a second unique reflector identifier; generating, by the first reflector, a first test reply to the actuator, the first test reply transmitted back to the actuator incorporating the first unique reflector identifier; generating, by the second reflector, a second test reply to the actuator, the second test reply transmitted back to the actuator incorporating the second unique reflector identifier; and using the first test reply and the second test reply to determine network performance metrics, wherein the first and second unique reflector identifiers are defined by the first reflector and the second reflector via a signaling exchange including a Two-Way Active Measurement Protocol (TWAMP) control plane or via a configuration method, including at least one of Command Line Interface (CLP, web-based configuration, and Extensible Markup Language (XML): the actuator generating a plurality of TWAMP requests, the plurality of TWAMP requests encapsulated as UDP packets, each UDP packet having a port number, the port number of each of the plurality of TWAMP requests being set to a unique pre-agreed value for the first reflector and the second reflector, the actuator transmitting the plurality of TWAMP requests in order to minimize the delay between the plurality of TWAMP requests.
 2. The method of claim 1, wherein the predetermined identifier further comprises a port number and an address, the address being the same as a node located downstream from the second reflector along the test path.
 3. The method of claim 1, wherein the sectionalize of the communication network comprises adding an additional actuator device between a first actuator device, and the first reflector or the second reflector.
 4. The method of claim 3, wherein the additional actuator device can also act as a third reflector device.
 5. The method of claim 1, wherein the predetermined identifier further comprises a layer 3 address.
 6. The method of claim 1, wherein the first reflector, when forwarding the test packet to a second reflector, generates a second predetermined identifier with a second layer 2 address corresponding to the second reflector.
 7. The method of claim 6, wherein the predetermined identifier and the second predetermined identifier each comprise a common layer 3 address.
 8. The system of claim 1 wherein the first and second unique reflector identifiers are defined by the first reflector and the second reflector via a signaling exchange including a Two-Way Active Measurement Protocol (TWAMP) control plane or via a configuration method, including at least one of Command Line Interface (CLI), web-based configuration, and Extensible Markup Language (XML): the actuator generating a plurality of TWAMP requests, the plurality of TWAMP requests encapsulated as UDP packets, each UDP packet having a port number, the port number of each of the plurality of TWAMP requests being set to a unique pre-agreed value for the first reflector and the second reflector, the actuator transmitting the plurality of TWAMP requests in order to minimize the delay between the plurality of TWAMP requests.
 9. A system for establishing service operations administration and maintenance (OAM) sessions in a communication network, the system comprising: an actuator configured to transmit a first test packet and a second test packet along a test path, the first test packet configured with a predetermined identifier and a first unique reflector identifier, the second test packet configured with the predetermined identifier and a second unique reflector identifier, the predetermined identifier comprising a layer 2 actuator address; a first reflector located downstream along the test path with respect to the actuator; a second reflector located downstream along the test path with respect to the first reflector; wherein the first reflector is programmed to receive the first test packet and in response, generating a first test reply to the actuator, the first test reply transmitted back to the actuator incorporating the first unique reflector identifier; wherein the second reflector is programmed to receive the second test packet and in response, generating a second test reply to the actuator, the second test reply transmitted back to the actuator incorporating the second unique reflector identifier; wherein the actuator is configured to use the first test reply and the second test reply to determine network performance metrics, and wherein the first and second unique reflector identifiers are defined by the first reflector and the second reflector via a signaling exchange including a Two-Way Active Measurement Protocol (TWAMP) control plane or via a configuration method, including at least one of Command Line Interface (CLP, web-based configuration, and Extensible Markup Language (XML): the actuator generating a plurality of TWAMP requests, the plurality of TWAMP requests encapsulated as UDP packets, each UDP packet having a port number, the port number of each of the plurality of TWAMP requests being set to a unique pre-agreed value for the first reflector and the second reflector, the actuator transmitting the plurality of TWAMP requests in order to minimize the delay between the plurality of TWAMP requests.
 10. A method of measuring performance metrics in a communications network, the method comprising: monitoring, by a plurality of reflectors, a plurality of test packets transmitted by an actuator, each of the plurality of test packets containing a management message, each of the plurality of test packets comprising an identifier corresponding to one of the plurality of reflectors, each of the plurality of test packets being addressed to a network device downstream along a test path with respect to the plurality of reflectors; transmitting by the actuator a first test packet and a second test packet, the first test packet configured with the predetermined identifier and a first unique reflector identifier, the second test packet configured with the predetermined identifier and a second unique reflector identifier; generating, by each of the plurality of reflectors, a test reply to the actuator, the test reply transmitted back to the actuator comprising network performance information; and the actuator using the reply from each of the plurality of reflectors to determine performance metrics, wherein the first and second unique reflector identifiers are defined by the first reflector and the second reflector via a signaling exchange including a Two-Way Active Measurement Protocol (TWAMP) control plane or via a configuration method, including at least one of Command Line Interface (CLP, web-based configuration, and Extensible Markup Language (XML): the actuator generating a plurality of TWAMP requests, the plurality of TWAMP requests encapsulated as UDP packets, each UDP packet having a port number, the port number of each of the plurality of TWAMP requests being set to a unique pre-agreed value for the first reflector and the second reflector, the actuator transmitting the plurality of TWAMP requests in order to minimize the delay between the plurality of TWAMP requests.
 11. The method of claim 10 wherein the test packets are UDP packets.
 12. The method of claim 10 wherein the management messages are TWAMP messages.
 13. The method of claim 10 wherein the plurality of test packets are transmitted by the actuator in order to minimize the delay between the transmission times of the plurality of test packets.
 14. The method of claim 10 wherein the performance metrics comprises at least one of one-way network delay, two-way network delay, and packet loss. 